ESET Inspect

Browse: 🏠 · Solutions · Connectors · Methods · Tables · Content · Parsers · ASIM Parsers · ASIM Products · 📊

Back to Connectors Index


Attribute Value
Connector ID ESETInspect
Publisher ESET Netherlands
Used in Solutions ESET Inspect
Collection Method Azure Function
Connector Definition Files ESETInspect_API_FunctionApp.json
Ingestion API HTTP Data Collector APIAzure Function code uses SharedKey/HTTP Data Collector API
Custom Log V1 Tables Yes 🔶 — ingests into tables with type-suffixed columns

This connector will ingest detections from ESET Inspect using the provided REST API. This API is present in ESET Inspect version 1.4 and later.

Tables Ingested

This connector ingests data into the following tables:

Table Transformations Ingestion API Lake-Only
ESETInspect_CL 🔶 ? ?

💡 Tip: Tables with Ingestion API support allow data ingestion via the Azure Monitor Data Collector API, which also enables custom transformations during ingestion.

Permissions

Resource Provider Permissions: - Workspace (Workspace): read and write permissions on the workspace are required. - Keys (Workspace): read permissions to shared keys for the workspace are required. See the documentation to learn more about workspace keys.

Custom Permissions: - Microsoft.Web/sites permissions: Read and write permissions to Azure Functions to create a Function App is required. See the documentation to learn more about Azure Functions. - Access to the ESET PROTECT console: Permissions to add users

Setup Instructions

⚠️ Note: These instructions were automatically generated from the connector's user interface definition file using AI and may not be fully accurate. Please verify all configuration steps in the Microsoft Sentinel portal.

NOTE: This connector uses Azure Functions to connect to ESET Inspect to pull its logs into Microsoft Sentinel. This might result in additional data ingestion costs. Check the Azure Functions pricing page for details.

(Optional Step) Securely store workspace and API authorization key(s) or token(s) in Azure Key Vault. Azure Key Vault provides a secure mechanism to store and retrieve key values. Follow these instructions to use Azure Key Vault with an Azure Function App.

1. Step 1 - Create an API user

  1. Log into the ESET PROTECT console with an administrator account, select the More tab and the Users subtab.
  2. Click on the ADD NEW button and add a native user.
  3. Create a new user for the API account. Optional: Select a Home group other than All to limit what detections are ingested.
  4. Under the Permission Sets tab, assign the Inspect reviewer permission set.
  5. Log out of the administrator account and log into the console with the new API credentials for validation, then log out of the API account. 5.

2. Step 2 - Copy Workspace ID and Key

IMPORTANT: Before deploying the ESET Inspect connector, have the Workspace ID and Workspace Primary Key (can be copied from the following) readily available. - Workspace ID: WorkspaceId Note: The value above is dynamically provided when these instructions are presented within Microsoft Sentinel. - Primary Key: PrimaryKey Note: The value above is dynamically provided when these instructions are presented within Microsoft Sentinel.

3. Step 3 - Deploy the Azure Resource Manager (ARM) Template

Use this method for automated deployment of the ESET Inspect connector using an ARM Tempate.

  1. Click the Deploy to Azure button below.

    Deploy To Azure 2. Select the preferred Subscription, Resource Group and Location. 3. Enter the Workspace ID, Workspace Key, API Username, API Password , enter the Inspect base URL and the first ID to start ingesting detections from. - The defailt starting ID is 0. This means that all detections will be ingested. - Note: If using Azure Key Vault secrets for any of the values above, use the@Microsoft.KeyVault(SecretUri={Security Identifier})schema in place of the string values. Refer to Key Vault references documentation for further details. 4. Mark the checkbox labelled I agree to the terms and conditions stated above. 5. Click Purchase to deploy.


Browse: 🏠 · Solutions · Connectors · Methods · Tables · Content · Parsers · ASIM Parsers · ASIM Products · 📊

Back to Connectors Index